Questions
2 of 24
Explain the Single Responsibility Principle (SRP) with an example.
Difficulty: 3/10
Single Responsibility Principle
SRP states that a class should have one responsibility and therefore one primary reason to change. It does not mean a class can contain only one method. A common violation is placing business logic, persistence, formatting and notification responsibilities into one class. I separate these concerns when they evolve independently.
javascript
- 1
SRP is about responsibility, not method count.
- 2
Separate concerns that change for different business or technical reasons.
- 3
Smaller responsibilities improve testability.
- 4
Avoid creating extremely granular classes without a meaningful reason.
- 5
Use cohesion as a practical indicator of whether SRP is being respected.
Follow-up Questions
- Does SRP mean one method per class?
- How do you identify multiple responsibilities?
- How does SRP improve testing?
- Can excessive application of SRP become over-engineering?